Our Process
The goal was to create an app for EDIT. focused on teachers, considering their needs, frustrations and goals.
Empathise
Research was a big part of this project as EDIT. currently has +70 teachers spread in 3 locations, teaching remotely and on-site in areas such as Data & Business, UX/UI Design, Programming and Digital Marketing. There was plenty of information, but it was scattered and fragmented.
We needed to understand what it meant to be a teacher at EDIT. and set off to interview our audience.
We needed to understand what it meant to be a teacher at EDIT. and set off to interview our audience.
After collecting and digesting all the information gathered during these interviews, we were in a place to define a persona that would guide our next steps.
Define
Teachers need their admin tasks to be agile and centralised so they can direct their allotted time for EDIT. to the core of their job: teaching.
We had four guiding principles in mind.
Functional - Features that optimise the course management
Efficient - Quick performance, reducing the time dedicated to day to day tasks
Intuitive - Straightforward navigation, making the experience more productive.
Collaborative - Simplify communication and allow knowledge sharing between teachers
This allowed us to have a clear focus when drafting the taskflows of the main features of the app, namely check-in and calendar management, classes, payments and files.
Check-in
Calendar management
Classes
Payments
Files
Ideate
The initial low fidelity wireframes allowed for some experimentation with a few teachers.
After a few iterations and some feedback, we understood we could make things simpler by changing the check-in method, thus reducing this action to 4 screens.
Design
Tests
We tested two features - check-in and calendar, which were also the most popular when we interviewed teachers. Both were successful, but we realised calendar management still needed some tweaks, as mentioned below on next steps.
Reflection and next steps
This project was especially challenging due to the variety of tools teachers use and the complexity of features that they can benefit from. There are challenges in adding a calendar on the app as it would mean a 3rd calendar for the user to look at, besides work and personal calendars.
Next steps:
- As any calendar changes need to be approved by the school, the edit event option needs to be Request change that has 1) teacher they want to swap with and 2) sends that request to the school operation centre.
- Develop the Logged hours area so teachers are access to their logged hours of work, connected with the check-in, and having the possibility to make changes or report mistakes. They should also get a monthly notification to remind them to confirm and submit their logs.
This project was especially challenging due to the variety of tools teachers use and the complexity of features that they can benefit from. There are challenges in adding a calendar on the app as it would mean a 3rd calendar for the user to look at, besides work and personal calendars.
Next steps:
- As any calendar changes need to be approved by the school, the edit event option needs to be Request change that has 1) teacher they want to swap with and 2) sends that request to the school operation centre.
- Develop the Logged hours area so teachers are access to their logged hours of work, connected with the check-in, and having the possibility to make changes or report mistakes. They should also get a monthly notification to remind them to confirm and submit their logs.
Project developed within UX/UI Design course at EDIT. with Ana Clara Silva, Inês Cunha and Raquel Strecht.
